Search for: All records

Abstract We present proper motion measurements of the oxygen-rich ejecta of the LMC supernova remnant N132D using two epochs of Hubble Space Telescope Advanced Camera for Surveys data spanning 16 years. The proper motions of 120 individual knots of oxygen-rich gas were measured and used to calculate a center of expansion (CoE) of α = 5 h 25 m 01.ˢ71 and δ = −69°38′41.″64 (J2000) with a 1 σ uncertainty of 2.″90. This new CoE measurement is 9.″2 and 10.″8 from two previous CoE estimates based on the geometry of the optically emitting ejecta. We also derive an explosion age of 2770 ± 500 yr, which is consistent with recent age estimates of ≈2500 yr made from 3D ejecta reconstructions. We verified our estimates of the CoE and age using a new automated procedure that detected and tracked the proper motions of 137 knots, with 73 knots that overlap with the visually identified knots. We find that the proper motions of the ejecta are still ballistic, despite the remnant’s age, and are consistent with the notion that the ejecta are expanding into an interstellar medium cavity. Evidence for explosion asymmetry from the parent supernova is also observed. Using the visually measured proper motion measurements and corresponding CoE and age, we compare N132D to other supernova remnants with proper motion ejecta studies. 

Abstract We analyze a sample of 45 Type II supernovae from the Zwicky Transient Facility public survey using a grid of hydrodynamical models in order to assess whether theoretically driven forecasts can intelligently guide follow-up observations supporting all-sky survey alert streams. We estimate several progenitor properties and explosion physics parameters, including zero-age main-sequence (ZAMS) mass, mass-loss rate, kinetic energy, 56 Ni mass synthesized, host extinction, and the time of the explosion. Using complete light curves we obtain confident characterizations for 34 events in our sample, with the inferences of the remaining 11 events limited either by poorly constraining data or the boundaries of our model grid. We also simulate real-time characterization of alert stream data by comparing our model grid to various stages of incomplete light curves (Δ t < 25 days, Δ t < 50 days, all data), and find that some parameters are more reliable indicators of true values at early epochs than others. Specifically, ZAMS mass, time of the explosion, steepness parameter β , and host extinction are reasonably constrained with incomplete light-curve data, whereas mass-loss rate, kinetic energy, and 56 Ni mass estimates generally require complete light curves spanning >100 days. We conclude that real-time modeling of transients, supported by multi-band synthetic light curves tailored to survey passbands, can be used as a powerful tool to identify critical epochs of follow-up observations. Our findings are relevant to identifying, prioritizing, and coordinating efficient follow-up of transients discovered by the Vera C. Rubin Observatory. 

Developing sustainable software for the scientific community requires expertise in software engineering and domain science. This can be challenging due to the unique needs of scientific software, the insufficient resources for software engineering practices in the scientific community, and the complexity of developing for evolving scientific contexts. While open‐source software can partially address these concerns, it can introduce complicating dependencies and delay development. These issues can be reduced if scientists and software developers collaborate. We present a case study wherein scientists from the SuperNova Early Warning System collaborated with software developers from the Scalable Cyberinfrastructure for Multi‐Messenger Astrophysics project. The collaboration addressed the difficulties of open‐source software development, but presented additional risks to each team. For the scientists, there was a concern of relying on external systems and lacking control in the development process. For the developers, there was a risk in supporting a user‐group while maintaining core development. These issues were mitigated by creating a second Agile Scrum framework in parallel with the developers' ongoing Agile Scrum process. This Agile collaboration promoted communication, ensured that the scientists had an active role in development, and allowed the developers to evaluate and implement the scientists' software requirements. The collaboration provided benefits for each group: the scientists actuated their development by using an existing platform, and the developers utilized the scientists' use‐case to improve their systems. This case study suggests that scientists and software developers can avoid scientific computing issues by collaborating and that Agile Scrum methods can address emergent concerns.